Network records for detecting impairments within a service provider network

ABSTRACT

Systems, methods, and apparatuses can detect whether an impairment is present within a service provider network. The impairment can cause a service provided by the service provider network to not perform as expected. These systems, methods, and apparatuses can develop multiple network records to record the performance of the service provider network at various instances in time. These systems, methods, and apparatuses can compare these network records among each other to detect for the presence of the impairment within the service provider network. These systems, methods, and apparatuses can thereafter diagnose and/or remedy the impairment when present within the service provider network.

BACKGROUND

A service provider network provides a service, such as communication ofvideo, audio, and/or data to provide some examples, to one or moresubscriber premises that are associated with one or more subscribers ofthe service. In some situations, an impairment, such an error, a fault,and/or a failure to provide some examples, can be present within theservice provider network. The error represents a human action thatproduces an incorrect result. As an example, the error can includefailing to plug the electronic device into an appropriate electricalsocket. The fault represents a manifestation of an error in anelectronic device of the service provider network, also known as adefect or a bug. The fault can be hardware-based that is manifested inthe hardware of the service provider network and/or software-based thatis manifested in the software executing within the service providernetwork. The failure represents a deviation of an electronic device ofthe service provider network from its intended operation. For example,the failure can occur when the electronic device produces the incorrectresult or does not perform the correct action. The error, the fault,and/or the failure can cause the service provided by the serviceprovider network to not perform as expected.

BRIEF DESCRIPTION OF THE DRAWINGS/FIGURES

The present disclosure is described with reference to the accompanyingdrawings. In the drawings, like reference numbers indicate identical orfunctionally similar elements. Additionally, the left most digit(s) of areference number identifies the drawing in which the reference numberfirst appears. In the accompanying drawings:

FIG. 1 graphically illustrates an exemplary service provider networkaccording to some exemplary embodiments of the present disclosure;

FIG. 2 illustrates a first flowchart of a first exemplary operation fordiagnosing and/or remedying an impairment within the exemplary serviceprovider network according to some exemplary embodiments of the presentdisclosure;

FIG. 3 illustrates a second flowchart of a second exemplary operationfor diagnosing and/or remedying the impairment within the exemplaryservice provider network according to some exemplary embodiments of thepresent disclosure;

FIG. 4 illustrates a third flowchart of a third exemplary operation fordiagnosing and/or remedying the impairment within the exemplary serviceprovider network according to some exemplary embodiments of the presentdisclosure;

FIG. 5 graphically illustrates an exemplary network record that can beutilized within the exemplary service provider network according to someexemplary embodiments of the present disclosure; and

FIG. 6 graphically illustrates a simplified block diagram of a computersystem suitable for use with embodiments described herein, as well ascircuit design and circuit embodiments of the technology, according toan exemplary embodiment of the present disclosure.

The present disclosure will now be described with reference to theaccompanying drawings.

DETAILED DESCRIPTION OF THE DISCLOSURE Overview

Systems, methods, and apparatuses disclosed herein can detect whether animpairment is present within a service provider network. In someembodiments, the impairment can cause a service provided by the serviceprovider network to not perform as expected. For example, the impairmentcan cause a black screen, pixelization of a movie or a televisionprogram, lack of sound for the movie or the television program,intermittent connectivity, slow speed, no internet connectivity, nodial-tone, and/or an inability to receive electronic mail (email)messages among others to provide some examples. As to be described infurther detail below, these systems, methods, and apparatuses candevelop multiple network records to record the performance of theservice provider network at various instances in time. In someembodiments, these systems, methods, and apparatuses can compare thesenetwork records among each other to detect for the presence of theimpairment within the service provider network. In these embodiments,these systems, methods, and apparatuses can thereafter diagnose and/orremedy the impairment when present within the service provider network.

Exemplary Service Provider Network

FIG. 1 graphically illustrates an exemplary service provider networkaccording to some exemplary embodiments of the present disclosure. Inthe exemplary embodiment illustrated in FIG. 1 , a service providernetwork 100 can detect whether an impairment is present within theservice provider network 100. As to be described in further detailbelow, the impairment can be present anywhere within the serviceprovider network 100, for example, one or more subscriber premises, suchas one or more customer home networks within the one or more subscriberpremises, a service provider system, a service personnel workstation,and/or a communication network of the service provider network 100. Insome embodiments, the impairment can cause a service provided by theservice provider network 100 to not perform as expected. For example,the impairment can cause a black screen, pixelization of a movie or atelevision program, lack of sound for the movie or the televisionprogram, intermittent connectivity, slow speed, no internetconnectivity, no dial-tone, and/or an inability to receive electronicmail (email) messages among others to provide some examples. As to bedescribed in further detail below, the service provider network 100 candevelop multiple network records to record the performance of theservice provider network 100 at various instances in time. In someembodiments, the service provider network 100 can compare these networkrecords among each other to detect for the presence of the impairmentwithin the service provider network 100. In these embodiments, theservice provider network 100 can thereafter diagnose and/or remedy theimpairment when present within the service provider network 100. In theexemplary embodiment illustrated in FIG. 1 , the service providernetwork 100 can include subscriber premises 102, a service providersystem 104, a service personnel workstation 106 that are communicativelycoupled to one another via a communication network 108.

The subscriber premises 102 represent one or more building and/ornon-building structures that receive the service from the serviceprovider network 100. Generally, the one or more building structuresrefer to any suitable structure or structures that are designed forhuman occupancy and can include one or more residential, industrial,and/or commercial building structures to provide some examples.Generally, the one or more non-building structures refer to any suitablestructure or structures that are not designed for human occupancy andcan include one or more residential, industrial, and/or commercialnon-building structures to provide some examples. In some embodiments,the subscriber premises 102 can include electronic devices that receivethe service from the service provider network 100 and/or access pointsthat facilitate the services between the service provider system 104 andthe electronic devices via the communication network 108. Generally, theone or more electronic devices represent any suitable mechanical,electrical, and/or electromechanical devices that can communicateelectronic information to and/or from the service provider system 104via the communication network 108 and/or the one or more access points.In some embodiments, the one or more electronic devices can includemobile telephony devices, such as mobile phones, mobile computingdevices, mobile internet devices, such as tablet computers and/or laptopcomputers, video game consoles, portable media players, peripheraldevices, such as wireless speakers, mice, keyboards, monitors, printers,and/or scanners, internet capable appliances, smart televisions, videostreaming devices, video set-top boxes (STBs), and/or other suitablecommunication devices that are capable of wireless communication thatwill be recognized by those skilled in the relevant art(s) withoutdeparting from the spirit and scope of the present disclosure.Generally, the one or more access points represent any suitablemechanical, electrical, and/or electromechanical devices that cancommunicate electronic information to and/or from the subscriberpremises 102 via the communication network 108. In some embodiments, theone or more access points can include wireless routers, cable modems,set-top boxes (STBs), digital subscriber line (DSL) modems, WiFi signalextenders, and/or other suitable communication devices that cancommunicate electronic information to and/or from the subscriberpremises 102 via the communication network 108 that will be recognizedby those skilled in the relevant art(s) without departing from thespirit and scope of the present disclosure.

The service provider system 104 represents one or more computer systems,an exemplary embodiment of which is to be described in further detailbelow, which facilitate delivery of the service to the subscriberpremises 102. In some embodiments, the service can include, for example,delivery of media content, such as movies, television programs,advertising, and/or electronic programing guides (EPGs) to provide someexamples, internet access, and/or telephone service. As illustrated inFIG. 1 , the service provider system 104 can detect whether theimpairment is present within the service provider network 100. Asdescribed above, the impairment can be present anywhere within theservice provider system 104 which includes the subscriber premises 102,such as one or more customer home networks within the subscriberpremises 102, as described above and the service provider system 104 asto be described in further detail below. And as to be described infurther detail below, the service provider system 104 can developmultiple network records to record the performance of the serviceprovider network 100 at various instances in time. In some embodiments,the service provider system 104 can compare these network records amongeach other to detect for the presence of the impairment within theservice provider network 100. In these embodiments, the service providersystem 104 can thereafter diagnose and/or remedy the impairment whenpresent within the service provider network 100. In the exemplaryembodiment illustrated in FIG. 1 , the service provider system 104 caninclude a service provider server 110, an administrative server 112, anetwork record repository 114, and/or an administrative workstation 116.

The service provider server 110 provides the service to the subscriberpremises 102 to deliver electronic information, such as video, audio,and/or data to provide some examples, to the subscriber premises 102 ina downstream direction. As used herein, the term “downstream direction”refers to the transfer of the electronic information from the serviceprovider system 104 to the subscriber premises 102. As part of theservice, the service provider server 110 can receive electronicinformation, such as video, audio, and/or data to provide some examples,from the subscriber premises 102 in an upstream direction. As usedherein, the term “upstream direction” refers to the transfer of theelectronic information from the subscriber premises 102 to the serviceprovider system 104.

The administrative server 112 represents one or more computer systems,an exemplary embodiment of which is to be described in further detailbelow, which manages the service. In the exemplary embodimentillustrated in FIG. 1 , the administrative server 112 can developnetwork records 118 to record the performance of the service providernetwork 100 at various instances in time. Alternatively, or in additionto, the administrative server 112 can store one or more of the networkrecords 118 in the network record repository 114 which is to bedescribed in further detail below. In some embodiments, these networkrecords can represent multiple “snapshots” of various characteristics,parameters, and/or attributes of the service provider network 100 thatcharacterize the performance of the service provider network 100 at thevarious instances in time. In these embodiments, these network recordscan represent multiple “snapshots” of various characteristics,parameters, and/or attributes of one or more of the subscriber premises102 that characterize the performance of the one or more of thesubscriber premises 102 at the various instances in time. In someembodiments, the various instances in time can be, or from among, aperiodic instances of time, such as every twenty-four (24) hours, everymultiple days, every week, or every month to provide some examples, anaperiodic instances of time, and/or in response to an event, such as aprovisioning of electronic devices and/or access points within thesubscriber premises 102, a service call being received from a subscriberassociated with the subscriber premises 102, and/or a service technicianarriving at and/or departing from the subscriber premises 102 to providesome examples.

In the exemplary embodiment illustrated in FIG. 1 , the administrativeserver 112 can determine one or more characteristics, parameters, and/orattributes of the service provider network 100 during the variousinstances in time to develop the network records 118. In someembodiments, the one or more characteristics, parameters, and/orattributes can include various parameters, characteristics, and/orattributes describing configuration information of one or more of thesubscriber premises 102, such as the configuration of the electronicdevices and/or the access points within one or more of the subscriberpremises 102 to provide an example. In these embodiments, theconfiguration information can include the make, model, type or brand ofthe electronic devices and/or the access points; one or more identifiersfor the network that is associated with the electronic devices and/orthe access points, such as a network identifier (ID) or a network nameto provide some examples; one or more locations of the electronicdevices and/or the access points; one or more device identifiers of theelectronic devices and/or the access points, such as a serial number, amedian access controller (MAC) address, and/or an Internet Protocol (IP)address to provide some examples; and/or one or more statuses of theelectronic devices and/or the access points, for example, power statusinformation, channel tuning information, device re-boot information,and/or software version installed on the electronic devices and/or theaccess points.

In some embodiments, the one or more characteristics, parameters, and/orattributes can include various parameters, characteristics, and/orattributes describing operation information of one or more of thesubscriber premises 102, such as the operation of the electronic devicesand/or the access points within one or more of the subscriber premises102 to provide an example. In these embodiments, the operationinformation can include provisioning information of the electronicdevices and/or the access points, such as a name of the subscriber, anaddress of the customer premise, an electronic mail address of thesubscriber, a telephone number associated with the subscriber, and/or apayment history of the subscriber. The operational information caninclude signal strengths of the electronic devices and/or the accesspoints, receiving signal strength of the electronic devices and/or theaccess points, transmitting signal strength of the electronic devicesand/or the access points, speeds of the downstream direction, speeds ofthe upstream direction, modulation of the digital data being carried,and/format of the digital data being carried to provide some examples.In some embodiments, the operational information can further includehealth information, for example, a heath score, of the electronic devicethat is associated with the selected graphical icon.

In some embodiments, the one or more characteristics, parameters, and/orattributes can include historical information that is associated withone or more of the subscriber premises 102, such as historicalinformation of the electronic devices and/or the access points withinone or more of the subscriber premises 102 to provide an example. Inthese embodiments, the historical information can identify one or moreimpairments that were previously present in the service provider network100, one or more potential sources of these impairments, and/or one ormore previous actions that were performed on these one or more potentialsources to remedy these impairments.

In the exemplary embodiment illustrated in FIG. 1 , the configurationinformation, the operation information, and/or the historicalinformation can include, or be related to, one or more radio frequency(RF) communication channels, such as one or more DOCSIS communicationchannels, that carry the service between the subscriber premises 102 andthe service provider system 104, one or more fiber optic communicationchannels that carry the service between the subscriber premises 102 andthe service provider system 104, the electronic devices and/or theaccess points within one or more of the subscriber premises 102, and/oroutcomes from one or more assessments of the service provider network100, such as a speed test or a Wi-Fi Service Set Identifier (SSID) checkto provide some examples.

Upon developing the network records 118, the administrative server 112can compare the network records 118 among each other to detect for thepresence of the impairment. In some embodiments, the administrativeserver 112 can autonomously compare the network records 118 among eachother to proactively monitor the service provider network 100 to detectfor the presence of the impairment. Alternatively, or in addition to,the administrative server 112 can compare the network records 118 amongeach other in response to an event, such as a provisioning of electronicdevices and/or access points within the subscriber premises 102, aservice call being received from a subscriber associated with thesubscriber premises 102, and/or a service technician arriving at and/ordeparting from the subscriber premises 102 to provide some examples, todetect for the presence of the impairment. In the exemplary embodimentillustrated in FIG. 1 , the service provider system 104 can compare oneor more characteristics, parameters, and/or attributes from a firstnetwork record that was developed at a first instance in time from amongthe network records 118 and one or more corresponding characteristics,parameters, and/or attributes from a second network record that wasdeveloped at a second instance in time from among the network records118 to detect for the presence of the impairment within the serviceprovider network 100. In some embodiments, the administrative server 112can develop the first network record at the first instance in time andcan retrieve the second network record from the network recordrepository 114 for comparison. In some embodiments, the administrativeserver 112 can determine that the impairment is present within theservice provider network 100 when the one or more characteristics,parameters, and/or attributes from the first network record differ fromthe one or more corresponding characteristics, parameters, and/orattributes from the second network record. Additionally, theadministrative server 112 can signal the service provider network 100 ofthe presence of the impairment. In some embodiments, this signaling caninclude dispatching a service technician to diagnose and/or remedy theimpairment when present within the service provider network 100 and/oralerting a subscriber of the service of the presence of the impairment.In these embodiments, the alerting can include sending an electronicmail (email) message and/or a short message service (SMS) text messageto a subscriber whose service is affected by the impairment to providesome examples.

The administrative server 112 can diagnose and/or remedy the impairmentupon detecting the presence of the impairment. In some embodiments, theadministrative server 112 can diagnose one or more mechanical,electrical, and/or electromechanical devices within the service providernetwork 100 causing different characteristics, parameters, and/orattributes between the first network record and the second networkrecord as causing of the impairment. In this example, the administrativeserver 112 can cause these mechanical, electrical, and/orelectromechanical devices to be repaired, for example, by dispatching aservice technician, and/or replaced, for example, by causing delivery ofa new mechanical, electrical, and/or electromechanical device, to remedythe impairment.

As illustrated in FIG. 1 , the administrative server 112 can store oneor more of the network records 118 in the network record repository 114.In some embodiments, the network record repository 114 can include oneor more non-transitory machine-readable mediums such as read only memory(ROM), random access memory (RAM), magnetic disk repository media,optical repository media, and/or flash memory devices to provide someexamples. In some embodiments, the administrative server 112 can storethe network records 118 as an organized collection of data, oftenreferred to as a database, within the network record repository 114. Inthese embodiments, a database may include one or more data tables havingvarious data values, such as alphanumeric strings, integers, decimals,floating points, dates, times, binary values, Boolean values, and/orenumerations to provide some examples. In some embodiments, the databasecan be a columnar database, a relational database, a key-store database,a graph database, and/or a document store to provide some examples.

The administrative workstation 116 represents one or more computersystems, an exemplary embodiment of which is to be described in furtherdetail below, which oversees the operation of the service providernetwork 100. In the exemplary embodiment illustrated in FIG. 1 , acustomer service representative of the service provider network 100operating the administrative workstation 116 can receive an inquiry,such as a telephone call, a short message service (SMS) text message, oran electronic mail (email) message to provide some examples, from asubscriber whose service is affected by the impairment. For example, theinquiry can indicate that the subscriber is experiencing a black screen,pixelization of a movie or a television program, lack of sound for themovie or television program, intermittent connectivity, slow speed, nointernet connectivity, no dial-tone, and/or an inability to receiveelectronic mail (email) messages to provide some examples. In someembodiments, the administrative server 112 and/or the administrativeworkstation 116 can compare the network records 118 among each other todetect for the presence of the impairment in a substantially similarmanner as described above. In these embodiments, the administrativeworkstation 116 can cause the administrative server 112 to develop oneof the network records 118 in response to the inquiry received from thesubscriber. As an example, the administrative server 112 can provide afirst network record that was developed at a first instance in time inresponse to the inquiry from among the network records 118 and a secondnetwork record that was developed at a second instance in time fromamong the network records 118 to the administrative workstation 116. Inthis example, the administrative workstation 116 can compare one or morecharacteristics, parameters, and/or attributes from the first networkrecord and one or more corresponding characteristics, parameters, and/orattributes from the second network record to detect for the presence ofthe impairment within the service provider network 100 in asubstantially similar manner as described above. In some embodiments,the administrative workstation 116 can further diagnose and/or remedythe impairment upon detecting the presence of the impairment in asubstantially similar manner as described above. As an example, theadministrative workstation 116 can dispatch a service technician to thesubscriber premises 102 and/or to cause one or more mechanical,electrical, and/or electromechanical devices to be replaced within theservice provider network 100 to remedy the impairment.

The service personnel workstation 106 represents one or more mobilecomputer systems which oversee the operation of the service providernetwork 100. In some embodiments, the service personnel workstation 106can be implemented as one or more mobile telephony devices, such as oneor more mobile phones, and/or one or more mobile computing devices, oneor more mobile internet devices, such as one or more tablet computersand/or one or more laptop computers, to provide some examples. In theexemplary embodiment illustrated in FIG. 1 , the service personnelworkstation 106 can compare the network records 118 among each other todetect for the presence of the impairment in a substantially similarmanner as described above. As described above, the impairment can bepresent anywhere within the service provider system 104 which includesthe service personnel workstation 106 and the communication network 108that are to be described in further detail below. In some embodiments,the service personnel workstation 106 can cause the administrativeserver 112 to develop one of the network records 118 in response to aservice technician associated with the service personnel workstation 106arriving and/or departing from one or more of the subscriber premises102. In these embodiments, this allows other service technicians thatmight be dispatched to the one or more of the subscriber premises 102 inthe future to easily identify the state of the one or more of thesubscriber premises 102. As an example, the administrative server 112can provide a first network record that was developed at a firstinstance in time in response to the service technician arriving and/ordeparting from the one or more of the subscriber premises 102 from amongthe network records 118 and a second network record that was developedat a second instance in time from among the network records 118 to theservice personnel workstation 106. In this example, the servicepersonnel workstation 106 can compare one or more characteristics,parameters, and/or attributes from the first network record and one ormore corresponding characteristics, parameters, and/or attributes fromthe second network record to detect for the presence of the impairmentwithin the service provider network 100 in a substantially similarmanner as described above. In some embodiments, the service personnelworkstation 106 can further diagnose and/or remedy the impairment upondetecting the presence of the impairment in a substantially similarmanner as described above. As an example, the service technician canreplace and/or repair one or more mechanical, electrical, and/orelectromechanical devices within the service provider network 100 toremedy the impairment.

The communication network 108 communicatively couples the subscriberpremises 102 and the service provider system 104. The communicationnetwork 108 can implemented as a wireless communication network, awireline communication network, and/or any combination thereof that willbe apparent to those skilled in the relevant art(s) without departingfrom the spirit and scope of the present disclosure. In someembodiments, the communication network 108 can include a hybridfiber-coaxial (HFC) network that combines optical fiber and coaxialcable to deliver the electronic information, such as the video, theaudio, and/or the data to provide some examples, from the serviceprovider system 104 to the subscriber premises 102 in the downstreamdirection and/or to deliver the electronic information from thesubscriber premises 102 to the service provider system 104 or in theupstream direction. In some embodiments, the communication network 108can include a fiber to the home (FIFTH) network that utilizes opticalfiber for at least a portion of the communication network 108 to deliverthe electronic information, such as the video, the audio, and/or thedata to provide some examples, from the service provider system 104 tothe subscriber premises 102 in the downstream direction and/or todeliver the electronic information from the subscriber premises 102 tothe service provider system 104 or in the upstream direction.

Exemplary Operations of the Exemplary Service Provider Network

FIG. 2 illustrates a first flowchart of a first exemplary operation fordiagnosing and/or remedying an impairment within the exemplary serviceprovider network according to some exemplary embodiments of the presentdisclosure. The disclosure is not limited to this operationaldescription. Rather, it will be apparent to ordinary persons skilled inthe relevant art(s) that other operational control flows are within thescope and spirit of the present disclosure. The following discussiondescribes an exemplary operational control flow 200 for diagnosingand/or remedying the impairment within a service provider network, suchas the service provider network 100. The operational control flow 200can be executed by one or more computer systems, such as the serviceprovider system 104 and/or the service personnel workstation 106 asdescribed above in FIG. 1 to provide some examples.

At operation 202, the operational control flow 200 develops a firstnetwork record at a first instance in time. In some embodiments, thefirst instance in time can be from among a periodic instances of time,such as every twenty-four (24) hours, every multiple days, every week,or every month to provide some examples, from among an aperiodicinstances of time, and/or in response to an event, such as aprovisioning of electronic devices and/or access points within thesubscriber premises 102, a service call being received from a subscriberassociated with the subscriber premises 102, and/or a service technicianarriving at and/or departing from the subscriber premises 102 to providesome examples. The first network record can represent an exemplaryembodiment of one of the network records 118 that are described above inFIG. 1 . The operational control flow 200 can develop the first networkrecord to record the performance of the service provider network at thefirst instance in time. In some embodiments, the first network recordcan include a “snapshot” of various characteristics, parameters, and/orattributes of the service provider network that characterize theperformance of the service provider network at the first instance intime. In these embodiments, the operational control flow 200 canmeasure, estimate, and/or select one or more characteristics,parameters, and/or attributes of the service provider network during thefirst instance in time to develop the first network record.

At operation 204, the operational control flow 200 compares the firstnetwork record from operation 202 with a second network record that wasdeveloped at a second instance in time. In some embodiments, the secondinstance in time can occur prior to the first instance in time. In theseembodiments, the second instance in time can be a prior instance of timefrom among the periodic instances of time, a prior instance of time fromamong the aperiodic instances of time, and/or in response to a priorevent, such as a prior provisioning of electronic devices and/or accesspoints within the subscriber premises 102, a prior service call beingreceived from a subscriber associated with the subscriber premises 102,and/or a prior service technician arriving at and/or departing from thesubscriber premises 102 to provide some examples. In these embodiments,the operational control flow 200 can retrieve the second network recordfrom a network record repository, such as the network record repository114 to provide an example, for comparison. At operation 204, theoperational control flow 200 can compare one or more characteristics,parameters, and/or attributes from the first network record fromoperation 202 and one or more corresponding characteristics, parameters,and/or attributes from the second network record.

At operation 206, the operational control flow 200 determines whetherthere is a difference between the first network record from operation202 and the second network record from operation 204 to detect for thepresence of the impairment within the service provider network. Asdescribed above, the impairment can be present anywhere within theservice provider network, for example, one or more subscriber premises,such as one or more customer home networks within the one or moresubscriber premises, a service provider system, a service personnelworkstation, and/or a communication network of the service providernetwork. In some embodiments, the operational control flow 200 candetermine that the impairment is present within the service providernetwork when the one or more characteristics, parameters, and/orattributes from the first network record from operation 202 differ fromthe one or more corresponding characteristics, parameters, and/orattributes from the second network record from operation 204. Theoperational control flow 200 reverts to operation 202 to develop anotherfirst network record when the one or more characteristics, parameters,and/or attributes from the first network record from operation 202 arethe same as the one or more corresponding characteristics, parameters,and/or attributes from the second network record from operation 204indicating that the impairment is not present within the serviceprovider network. Otherwise, the operational control flow 200 proceedsto operation 208 when the one or more characteristics, parameters,and/or attributes from the first network record from operation 202 aredifferent from the one or more corresponding characteristics,parameters, and/or attributes from the second network record fromoperation 204 indicating that the impairment is present within theservice provider network.

At operation 208, the operational control flow 200 can diagnose and/orremedy the impairment detected at operation 206 within the serviceprovider network. In some embodiments, the operational control flow 200can diagnose one or more mechanical, electrical, and/orelectromechanical devices within the service provider network causingdifferent characteristics, parameters, and/or attributes between thefirst network record and the second network record as being the cause ofthe impairment. In this example, the operational control flow 200 cancause these mechanical, electrical, and/or electromechanical devices tobe repaired, for example, by dispatching a service technician, and/orreplaced, for example, by causing delivery of a new mechanical,electrical, and/or electromechanical device, to remedy the impairment.Alternatively, or in addition to, the operational control flow 200 cansignal the service provider network of the presence of the impairmentdetected at operation 206. In some embodiments, this signaling caninclude dispatching a service technician to diagnose and/or remedy theimpairment detected at operation 206 and/or alerting a subscriber of theservice of the presence of the impairment detected at operation 206. Inthese embodiments, the alerting can include sending an electronic mail(email) message and/or a short message service (SMS) text message to asubscriber whose service is affected by the impairment detected atoperation 206 to provide some examples.

FIG. 3 illustrates a second flowchart of a second exemplary operationfor diagnosing and/or remedying the impairment within the exemplaryservice provider network according to some exemplary embodiments of thepresent disclosure. The disclosure is not limited to this operationaldescription. Rather, it will be apparent to ordinary persons skilled inthe relevant art(s) that other operational control flows are within thescope and spirit of the present disclosure. The following discussiondescribes an exemplary operational control flow 300 for diagnosingand/or remedying the impairment within a service provider network, suchas the service provider network 100. The operational control flow 300can be executed by one or more computer systems, such as theadministrative workstation 116 as described above in FIG. 1 to providesome examples.

At operation 302, the operational control flow 300 receives an inquiryfrom a subscriber of a service provided by the service provider networkwhose service is affected by an impairment that causes the service tonot perform as expected. As described above, the impairment can bepresent anywhere within the service provider network, for example, oneor more subscriber premises, such as one or more customer home networkswithin the one or more subscriber premises, a service provider system, aservice personnel workstation, and/or a communication network of theservice provider network. In some embodiments, a customer servicerepresentative of the service provider network operating theadministrative workstation 116 can receive an inquiry, such as atelephone call, a short message service (SMS) text message, or anelectronic mail (email) message to provide some examples, from thesubscriber whose service is affected by the impairment. For example, theinquiry can indicate that the subscriber is experiencing a black screen,pixelization of a movie or a television program, lack of sound for themovie or television program, intermittent connectivity, slow speed, nointernet connectivity, no dial-tone, and/or an inability to receiveelectronic mail (email) messages to provide some examples.

At operation 304, the operational control flow 300 develops a firstnetwork record in response to the inquiry from operation 302. The firstnetwork record can represent an exemplary embodiment of one of thenetwork records 118 that are described above in FIG. 1 . The operationalcontrol flow 300 can develop the first network record in response to theinquiry from operation 302 to record the performance of the serviceprovider network. In some embodiments, the first network record caninclude a “snapshot” of various characteristics, parameters, and/orattributes of the service provider network that characterize theperformance of the service provider network. In these embodiments, theoperational control flow 300 can measure, estimate, and/or select one ormore characteristics, parameters, and/or attributes of the serviceprovider network in response to the inquiry from operation 302 todevelop the first network record.

At operation 306, the operational control flow 300 identifies theimpairment from operation 302 based upon a difference between the firstnetwork record from operation 302 and a second network record that wasdeveloped prior to receiving the inquiry from operation 302. In someembodiments, the operational control flow 300 can determine which one ormore characteristics, parameters, and/or attributes differ between thefirst network record from operation 304 and the second network record.In these embodiments, these differences between the first network recordfrom operation 302 and the second network record can be characterized asbeing related to, for example, causing, the impairment from operation302.

At operation 308, the operational control flow 300 can diagnose and/orremedy the impairment from operation 302. In some embodiments, theoperational control flow 300 can diagnose one or more mechanical,electrical, and/or electromechanical devices within the service providernetwork causing the impairment from operation 302. In this example, theoperational control flow 300 can cause these mechanical, electrical,and/or electromechanical devices to be repaired, for example, bydispatching a service technician, and/or replaced, for example, bycausing delivery of a new mechanical, electrical, and/orelectromechanical device, to remedy the impairment. Alternatively, or inaddition to, the operational control flow 300 can signal the serviceprovider network of the presence of the impairment from operation 302.In some embodiments, this signaling can include dispatching a servicetechnician to diagnose and/or remedy the impairment from operation 302and/or alerting the subscriber from operation 302, or another subscriberof the service, of the presence of the impairment from operation 302. Inthese embodiments, the alerting can include sending an electronic mail(email) message and/or a short message service (SMS) text message to thesubscriber from operation 302, or the other subscriber, to provide someexamples.

FIG. 4 illustrates a third flowchart of a third exemplary operation fordiagnosing and/or remedying the impairment within the exemplary serviceprovider network according to some exemplary embodiments of the presentdisclosure. The disclosure is not limited to this operationaldescription. Rather, it will be apparent to ordinary persons skilled inthe relevant art(s) that other operational control flows are within thescope and spirit of the present disclosure. The following discussiondescribes an exemplary operational control flow 400 for diagnosingand/or remedying the impairment within a service provider network, suchas the service provider network 100. The operational control flow 400can be executed by one or more computer systems, such as the servicepersonnel workstation 106 as described above in FIG. 1 to provide someexamples.

At operation 402, the operational control flow 400 dispatches a servicetechnician of the service provider network to a subscriber premises todiagnose and/or remedy an impairment that causes a service provided bythe service provider network to not perform as expected. The subscriberpremises can represent an exemplary embodiment of one of the subscriberpremises 102 that are described above in FIG. 1 . In some embodiments, acustomer service representative of the service provider network canreceive an inquiry, such as a telephone call, a short message service(SMS) text message, or an electronic mail (email) message to providesome examples, from the subscriber whose service is affected by theimpairment. For example, the inquiry can indicate that the subscriber isexperiencing a black screen, pixelization of a movie or a televisionprogram, lack of sound for the movie or television program, intermittentconnectivity, slow speed, no internet connectivity, no dial-tone, and/oran inability to receive electronic mail (email) messages to provide someexamples. In this example, the customer service representative candispatch the service technician to the subscriber premises to diagnoseand/or remedy the black screen, the pixelization of the movie or thetelevision program, the lack of sound for the movie or televisionprogram, the intermittent connectivity, the slow speed, the no internetconnectivity, the no dial-tone, and/or the inability to receiveelectronic mail (email) messages to provide some examples.

At operation 404, the operational control flow 400 develops a firstnetwork record in response to the service technician from operation 402arriving at the subscriber premises. The first network record canrepresent an exemplary embodiment of one of the network records 118 thatare described above in FIG. 1 . The operational control flow 400 candevelop the first network record to record the performance of theservice provider network upon the service technician from operation 402arriving at the subscriber premises. In some embodiments, the firstnetwork record can include a “snapshot” of various characteristics,parameters, and/or attributes of the service provider network thatcharacterize the performance of the service provider network upon theservice technician from operation 402 arriving at the subscriberpremises. In these embodiments, the operational control flow 400 canmeasure, estimate, and/or select one or more characteristics,parameters, and/or attributes of the service provider network upon theservice technician from operation 402 arriving at the subscriberpremises to develop the first network record.

At operation 406, the operational control flow 400 identifies theimpairment from operation 402 based upon a difference between the firstnetwork record from operation 402 and a second network record that wasdeveloped prior to the service technician from operation 402 arriving atthe subscriber premises. In some embodiments, the operational controlflow 400 can determine which one or more characteristics, parameters,and/or attributes differ between the first network record from operation404 and the second network record. In these embodiments, thesedifferences between the first network record from operation 402 and thesecond network record can be characterized as being related to, forexample, causing, the impairment from operation 402.

At operation 408, the operational control flow 400 can diagnose and/orremedy the impairment from operation 402. In some embodiments, theoperational control flow 400 can diagnose one or more mechanical,electrical, and/or electromechanical devices within the service providernetwork causing the impairment from operation 402. In this example, theoperational control flow 400 can cause the service technician fromoperation 402 to repair and/or replace these mechanical, electrical,and/or electromechanical devices to remedy the impairment.

At operation 410, the operational control flow 400 develops a thirdnetwork record in response to the service technician from operation 402departing from the subscriber premises. The third network record canrepresent an exemplary embodiment of one of the network records 118 thatare described above in FIG. 1 . The operational control flow 400 candevelop the third network record to record the performance of theservice provider network upon the service technician from operation 402departing from the subscriber premises. In some embodiments, the thirdnetwork record can include a “snapshot” of various characteristics,parameters, and/or attributes of the service provider network thatcharacterize the performance of the service provider network upon theservice technician from operation 402 departing from subscriberpremises. In these embodiments, the operational control flow 400 canmeasure, estimate, and/or select one or more characteristics,parameters, and/or attributes of the service provider network upon theservice technician from operation 402 departing at the subscriberpremises to develop the third network record. The third network recordallows other service technicians of the service provider network toverify that the impairment from operation 402 has been remedied inoperation 408.

Exemplary Network Record that can be Utilized within the ExemplaryService Provider Network

FIG. 5 graphically illustrates an exemplary network record that can beutilized within the exemplary service provider network according to someexemplary embodiments of the present disclosure. One or more computersystems of a service provider network, such as the administrative server112 of the service provider network 100 to provide an example, candevelop network records, such as one or more of the network records 118as described above in FIG. 1 to provide an example, to record theperformance of a subscriber premises, such as one or more of thesubscriber premises 102 to provide an example, in delivering a serviceprovided by the service provider network at various instances in time.In some embodiments, these computer systems can compare these networkrecords among each other to detect for the presence of an impairmentwithin the service provider network that can cause the service to notperform as expected in a substantially similar manner as described abovein FIG. 1 . The discussion of FIG. 5 to follow is to describe anexemplary embodiment of one or more of these network records. However,those skilled in the relevant art(s) will recognize that other networkrecords are possible without departing from the spirit and scope of thepresent disclosure.

In the exemplary embodiment illustrated in FIG. 5 , a network record 500includes network record fields 502 having corresponding values fromamong network record values 504. Generally, the network record fields502 represent exemplary characteristics, parameters, and/or attributesof the subscriber premises that characterize the performance of thesubscriber premises in delivering the service at the specific instancein time. However, the exemplary characteristics, parameters, and/orattributes of the service provider network are for exemplary purposesonly. Those skilled in the relevant art(s) with recognize that othercharacteristics, parameters, and/or attributes of the subscriberpremises are possible for the network record 500 without departing fromthe spirit and scope of the present disclosure. Generally, the networkrecord values 504 can be characterized as being various alphabetical,numerical, and/or alphanumerical values. In some embodiments, thenetwork record values 504 can be assigned to various color codes toallow a customer service representative and/or a service technicianviewing the network record 500 to quickly identify the characteristics,parameters, and/or attributes of the service provider network that arecausing the impairment. For example, the network record values 504 canbe assigned to a first color code, such as green, when the networkrecord values 504 are conducive to delivering the service or to a secondcolor code, such as red, when the network record values 504 are notconducive to delivering the service. Exemplary green and/or red colorcodes for the network record values 504 are illustrated in FIG. 5 .

As illustrated in FIG. 5 , the network record 500 represents “snapshot”of network record fields 502 that characterize the performance of thesubscriber premises at the various instances in time. In the exemplaryembodiment illustrated in FIG. 5 , the network record fields 502 caninclude an <<access point radio frequency (RF) level check>> field 506,an <<access point online check>> field 508, an <<WiFi extender status>>field 510, a <<DOCSIS RF parameters>> field 512, and/or a <<Video STBstatus>> field 514.

In the exemplary embodiment illustrated in FIG. 5 , the <<access pointRF level check>> field 506 indicates whether the signal strength of theradio waves that are received by an access point of the subscriberpremises are sufficient to deliver the service. Generally, the radiowaves should have a signal strength, for example, greater than −55 dBmto ensure the subscriber premises delivers the best service. In someembodiments, a signal strength, for example, greater than −70 dBm isacceptable but may result in a degraded service, for example, poor videoexperience, being delivered by the subscriber premises. In someembodiments, a signal strength less than, for example, −70 dBm oftenresults in a severely degraded experience being delivered by thesubscriber premises. As illustrated in FIG. 5 , the network recordvalues 504 for the <<access point RF level check>> field 506 can be a<<PASS>> value to indicate that the radio waves received by the accesspoint have a signal strength, for example, greater than −70 dBm or a<<FAIL>> value to indicate that the radio waves received by the accesspoint have a signal strength, for example, greater less than −70 dBm. Itshould be noted that the various signal strengths, for example, −70 dBm,referred to in the description of FIG. 5 are for illustrative purposesonly and not limiting. Those skilled in the relevant art(s) will othersignal strengths are possible without departing from the spirit andscope of the present disclosure. As an example, different wirelesstechnologies, for example, WiFi6, WiFI6E, and/or WiFi7 can havedifferent signal strengths than those as described within thedescription of FIG. 5 . In the exemplary embodiment illustrated in FIG.5 , the <<access point online check>> field 508 identifies whether theaccess point of the subscriber premises is online to deliver theservice. As illustrated in FIG. 5 , the network record values 504 forthe <<access point online check>> field 508 can be a <<PASS>> value toindicate that the subscriber premises is online to deliver the serviceor a <<FAIL>> value to indicate that the subscriber premises is offlineand cannot deliver the service.

In the exemplary embodiment illustrated in FIG. 5 , the <<WiFi extenderstatus>> field 510 identifies one or more parameters, characteristics,and/or attributes relating to one or more WiFi signal extenders withinthe subscriber premises. As illustrated in FIG. 5 , the <<WiFi extenderstatus>> field 510 can include an <<on account>> field 516 having anumerical value from among the network record values 504 indicating thenumber of WiFi signal extenders within the subscriber premises and an<<online>> field 518 having a numerical value from among the networkrecord values 504 indicating the number of WiFi signal extenders withinthe subscriber premises that are online. In the exemplary embodimentillustrated in FIG. 5 , the <<WiFi extender status>> field 510 canfurther include one or more parameters, characteristics, and/orattributes for each of the WiFi signal extenders, denoted as WiFi signalextenders 520.1 through 520.a, within the subscriber premises. In someembodiments, the <<WiFi extender status>> field 510 can further include<<device median access controller (MAC) address>> fields 522,<<placement>> fields 524, and/or <<connection status>> fields 526 foreach of the WiFi signal extenders 520.1 through 520.a within thesubscriber premises. As illustrated in FIG. 5 , the network recordvalues 504 for the <<device median access controller (MAC) address>>fields 522 can be alphanumerical values. As illustrated in FIG. 5 , thenetwork record values 504 for the <<placement>> fields 524 can be an<<OPTIMAL>> value to indicate that the corresponding WiFi signalextender is optimally placed within the subscriber premises, a<<FAIL—TOO FAR>> value to indicate that the corresponding WiFi signalextender is too far from the access point of the subscriber premises interms of distance, or a <<FAIL—TOO CLOSE>> value to indicate that thecorresponding WiFi signal extender is too close from the access point ofthe subscriber premises in terms of distance. As illustrated in FIG. 5 ,the network record values 504 for the <<connection status>> fields 526can be an <<ONLINE>> value to indicate that the corresponding WiFisignal extender is online to deliver the service or an <<OFFLINE>> valueto indicate that the corresponding WiFi signal extender is offline andcannot deliver the service.

In the exemplary embodiment illustrated in FIG. 5 , the <<DOCSIS RFparameters>> field 512 identifies one or more parameters,characteristics, and/or attributes relating the delivery of electronicinformation, such as video, audio, and/or data to provide some examples,to the subscriber premises in the downstream direction and/or from thesubscriber premises in the upstream direction. As illustrated in FIG. 5, the <<DOCSIS RF parameters>> field 512 includes a <<downstreamdirection>> field 528.1 and an <<upstream direction>> field 528.2. Insome embodiments, the downstream direction>> field 528.1 includes a<<number of downstream channels>> field 530.1 that identifies the numberof downstream channels being used to deliver the electronic informationin the downstream direction, a <<number of downstream channelsimpaired>> field 532.1 that identifies the number of downstream channelsthat are impaired, an <<average received power>> field 534.1 thatidentifies the signal strength of the signals carrying the electronicinformation in the downstream direction and/or a <<minimum downstreamsignal-to-noise ratio (SNR)>> field 536.1 that identifies the signal tonoise ratio of the signals carrying the electronic information in thedownstream direction. Generally, the <<average received power>> field534.1 should have a signal strength, for example, between −8 dBm and 8dBm to ensure the subscriber premises delivers the best service. In someembodiments, a signal strength, for example, between −15 dBm and 15 dBmfor the <<average received power>> field 534.1 is acceptable. In someembodiments, a signal strength, for example, less than −15 dBm and/orgreater than 15 dBm often results in a severely degraded experiencebeing delivered by the subscriber premises. Generally, a received signalstrength indicator (RSSI) value for the <<minimum downstream SNR>> field536.1 should be, for example, greater than 30 dB. In some embodiments,the RSSI value for the <<minimum downstream SNR>> field 536.1 being, forexample, less than 25 dB often results in a severely degraded experiencebeing delivered by the subscriber premises.

In some embodiments, the upstream direction>> field 528.2 includes a<<number of upstream channels>> field 530.2 that identifies the numberof upstream channels being used to deliver the electronic information inthe upstream direction, a <<number of upstream channels impaired>> field532.2 that identifies the number of upstream channels that are impaired,an <<average received power>> field 534.2 that identifies the signalstrength of the signals carrying the electronic information in theupstream direction and/or a <<minimum upstream signal-to-noise ratio(SNR)>> field 536.2 that identifies the signal to noise ratio of thesignals carrying the electronic information in the upstream direction.Generally, the <<average received power>> field 534.2 should have asignal strength between 40 dBm and 50 dBm to ensure the subscriberpremises delivers the best service. In some embodiments, a signalstrength, for example, between 35 dBm and 55 dBm for the <<averagereceived power>> field 534.2 is acceptable. Generally, a received signalstrength indicator (RSSI) value for the <<minimum upstream SNR>> field536.2 should be, for example, greater than 30 dB. In some embodiments,the RSSI value for the <<minimum upstream SNR>> field 536.2 being, forexample, less than 25 dB often results in a severely degraded experiencebeing delivered by the subscriber premises.

In the exemplary embodiment illustrated in FIG. 5 , the <<video STBstatus>> field 514 identifies one or more parameters, characteristics,and/or attributes relating to one or more video set-top boxes (STBs)within the subscriber premises. As illustrated in FIG. 5 , the <<videoSTB status >> field 514 can include one or more parameters,characteristics, and/or attributes for each of the one or more videoSTBs, denoted as video STBs 530.1 through 530.b, within the subscriberpremises. In some embodiments, the <<video STB status>> field 514 caninclude <<device median access controller (MAC) address>> fields 532,<<status>> fields 534, <<connection status>> fields 536, <<connectiontype>> fields 538, <<placement>> fields 540, <<RSSI>> fields 542, and<<WIFI band>> fields 544 for each of the video STBs 530.1 through 530.bwithin the subscriber premises. As illustrated in FIG. 5 , the networkrecord values 504 for the <<device median access controller (MAC)address>> fields 532 can be alphanumerical values. As illustrated inFIG. 5 , the network record values 504 for the <<status>> fields 534 canbe a <<PASS>> value to indicate that the subscriber premises is onlineto deliver the service or a <<FAIL>> value to indicate that thesubscriber premises is offline and cannot deliver the service. Asillustrated in FIG. 5 , the network record values 504 for the<<connection status>> fields 536 can be an <<ONLINE>> value to indicatethat the corresponding video STB is online to deliver the service or an<<OFFLINE>> value to indicate that the corresponding video STB isoffline and cannot deliver the service. As illustrated in FIG. 5 , thenetwork record values 504 for the <<connection type>> fields 538 can bewired or wireless As illustrated in FIG. 5 , the network record values504 for the <<placement>> fields 540 can be an <<OPTIMAL>> value toindicate that the corresponding video STB is optimally placed within thesubscriber premises or a <<FAIL—TOO FAR>> value to indicate that thecorresponding video STB is too far from the access point of thesubscriber premises in terms of distance. As illustrated in FIG. 5 , thenetwork record values 504 for the <<RSSI>> fields 542 can be a numericalvalue indicating the received signal strength of the radio waves thatare received by the corresponding video STB. As illustrated in FIG. 5 ,the network record values 504 for the <<WIFI band>> fields 544 can be<<5 GHz>> when the corresponding video STB is operating in the 5 GHzunlicensed band, <<2.4 GHz>> when the corresponding video STB isoperating in the 2.4 GHz unlicensed band, or <<NA>> if the <<connectiontype>> fields 538 indicate the corresponding video STB is wired.

Exemplary Computer System that can be Utilized within the ExemplaryService Provider Network

FIG. 6 graphically illustrates a simplified block diagram of a computersystem suitable for use with embodiments described herein, as well ascircuit design and circuit embodiments of the technology, according toan exemplary embodiment of the present disclosure. The variouselectronic devices, for example, the service provider system 202 and/orthe portable diagnostic system 116, as described above can beimplemented in hardware, firmware, software, or any combination thereof.The discussion of FIG. 6 to follow describes an exemplary computersystem 610 that can be used for these electronic devices.

In the exemplary embodiment illustrated in FIG. 6 , the computer system610 typically includes at least one processor 614 which communicateswith a number of peripheral devices via bus subsystem 612. Typically,the at least processor 614 can include, or can be, any of amicroprocessor, graphics processing unit, or digital signal processor,and their electronic processing equivalents, such as an ApplicationSpecific Integrated Circuit (“ASIC”) or Field Programmable Gate Array(“FPGA”). As used herein, the term “processor” signifies a tangible dataand information processing device that physically transforms data andinformation, typically using a sequence transformation (also referred toas “operations”). Data and information can be physically represented byan electrical, magnetic, optical or acoustical signal that is capable ofbeing stored, accessed, transferred, combined, compared, or otherwisemanipulated by the processor. The term “processor” can signify asingular processor and multi-core systems or multi-processor arrays,including graphic processing units, digital signal processors, digitalprocessors or combinations of these elements. The processor can beelectronic, for example, comprising digital logic circuitry (forexample, binary logic), or analog (for example, an operationalamplifier). The processor may also operate to support performance of therelevant operations in a “cloud computing” environment or as a “softwareas a service” (SaaS). For example, at least some of the operations maybe performed by a group of processors available at a distributed orremote system, these processors accessible via a communications network(e.g., the Internet) and via one or more software interfaces (e.g., anapplication program interface (API).)

The computer system typically includes an operating system, such asMicrosoft's Windows, Sun Microsystems's Solaris, Apple Computer's MacOs,Linux or UNIX. The computer system also typically can include a BasicInput/Output System (BIOS) and processor firmware. The operating system,BIOS and firmware are used by the processor to control subsystems andinterfaces coupled to the processor. Typical processors compatible withthese operating systems include the Pentium and Itanium from Intel, theOpteron and Athlon from Advanced Micro Devices, and the ARM processorfrom ARM Holdings.

As illustrated in FIG. 6 , these peripheral devices may include astorage subsystem 624, comprising a memory subsystem 626 and a filestorage subsystem 628, user interface input devices 622, user interfaceoutput devices 620, and a network interface subsystem 616. The input andoutput devices allow user interaction with computer system 610. In theexemplary embodiment illustrated in FIG. 6 , the network interfacesubsystem 616 provides an interface to outside networks, including aninterface to a communication network 618, and is coupled via acommunication network 618 to corresponding interface devices in othercomputer systems or machines. The communication network 618 may comprisemany interconnected computer systems, machines and communication links.These communication links may be wired links, optical links, wirelesslinks, or any other devices for communication of information. Thecommunication network 618 can be any suitable computer network, forexample a wide area network such as the Internet, and/or a local areanetwork such as Ethernet. The communication network 618 can be wiredand/or wireless, and the communication network can use encryption anddecryption methods, such as is available with a virtual private network.The communication network uses one or more communications interfaces,which can receive data from, and transmit data to, other systems.Embodiments of communications interfaces typically include an Ethernetcard, a modem (e.g., telephone, satellite, cable, or ISDN),(asynchronous) digital subscriber line (DSL) unit, Firewire interface,USB interface, and the like. One or more communications protocols can beused, such as HTTP, TCP/IP, RTP/RTSP, IPX and/or UDP.

The user interface input devices 622 may include an alphanumerickeyboard, a keypad, pointing devices such as a mouse, trackball,touchpad, stylus, or graphics tablet, a scanner, a touchscreenincorporated into the display, audio input devices such as voicerecognition systems or microphones, eye-gaze recognition, brainwavepattern recognition, and other types of input devices. Such devices canbe connected by wire or wirelessly to a computer system. In general, useof the term “input device” is intended to include all possible types ofdevices and ways to input information into the computer system 610 oronto the communication network 618. The user interface input devices 622typically allow a user to select objects, icons, text and the like thatappear on some types of user interface output devices, for example, adisplay subsystem.

The user interface output devices 620 may include a display subsystem, aprinter, a fax machine, or non-visual displays such as audio outputdevices. The display subsystem may include a cathode ray tube (CRT), aflat-panel device such as a liquid crystal display (LCD), a projectiondevice, or some other device for creating a visible image such as avirtual reality system. The display subsystem may also providenon-visual display such as via audio output or tactile output (e.g.,vibrations) devices. In general, use of the term “output device” isintended to include all possible types of devices and ways to outputinformation from the computer system 610 to the user or to anothermachine or computer system.

The memory subsystem 626 typically includes a number of memoriesincluding a main random-access memory (“RAM”) 630 (or other volatilestorage device) for storage of instructions and data during programexecution and a read only memory (“ROM”) 632 in which fixed instructionsare stored. The file storage subsystem 628 provides persistent storagefor program and data files, and may include a hard disk drive, a floppydisk drive along with associated removable media, a CD-ROM drive, anoptical drive, a flash memory, or removable media cartridges. Thedatabases and modules implementing the functionality of certainembodiments may be stored by file storage subsystem 628.

The bus subsystem 612 provides a device for letting the variouscomponents and subsystems of the computer system 610 communicate witheach other as intended. Although the bus subsystem 612 is shownschematically as a single bus, alternative embodiments of the bussubsystem may use multiple busses. For example, RAM-based main memorycan communicate directly with file storage systems using Direct MemoryAccess (“DMA”) systems.

CONCLUSION

The Detailed Description referred to accompanying figures to illustrateexemplary embodiments consistent with the disclosure. References in thedisclosure to “an exemplary embodiment” indicates that the exemplaryembodiment described can include a particular feature, structure, orcharacteristic, but every exemplary embodiment may not necessarilyinclude the particular feature, structure, or characteristic. Moreover,such phrases are not necessarily referring to the same exemplaryembodiment. Further, any feature, structure, or characteristic describedin connection with an exemplary embodiment can be included,independently or in any combination, with features, structures, orcharacteristics of other exemplary embodiments whether or not explicitlydescribed.

The Detailed Description is not meant to limiting. Rather, the scope ofthe disclosure is defined only in accordance with the following claimsand their equivalents. It is to be appreciated that the DetailedDescription section, and not the Abstract section, is intended to beused to interpret the claims. The Abstract section can set forth one ormore, but not all exemplary embodiments, of the disclosure, and thus,are not intended to limit the disclosure and the following claims andtheir equivalents in any way.

The exemplary embodiments described within the disclosure have beenprovided for illustrative purposes and are not intended to be limiting.Other exemplary embodiments are possible, and modifications can be madeto the exemplary embodiments while remaining within the spirit and scopeof the disclosure. The disclosure has been described with the aid offunctional building blocks illustrating the implementation of specifiedfunctions and relationships thereof. The boundaries of these functionalbuilding blocks have been arbitrarily defined herein for the convenienceof the description. Alternate boundaries can be defined so long as thespecified functions and relationships thereof are appropriatelyperformed.

Embodiments of the disclosure can be implemented in hardware, firmware,software application, or any combination thereof. Embodiments of thedisclosure can also be implemented as instructions stored on amachine-readable medium, which can be read and executed by one or moreprocessors. A machine-readable medium can include any mechanism forstoring or transmitting information in a form readable by a machine(e.g., a computing circuitry). For example, a machine-readable mediumcan include non-transitory machine-readable mediums such as read onlymemory (ROM); random access memory (RAM); magnetic disk storage media;optical storage media; flash memory devices; and others. As anotherexample, the machine-readable medium can include transitorymachine-readable medium such as electrical, optical, acoustical, orother forms of propagated signals (e.g., carrier waves, infraredsignals, digital signals, etc.). Further, firmware, softwareapplication, routines, instructions can be described herein asperforming certain actions. However, it should be appreciated that suchdescriptions are merely for convenience and that such actions in factresult from computing devices, processors, controllers, or other devicesexecuting the firmware, software application, routines, instructions,etc.

The Detailed Description of the exemplary embodiments fully revealed thegeneral nature of the disclosure that others can, by applying knowledgeof those skilled in relevant art(s), readily modify and/or adapt forvarious applications such exemplary embodiments, without undueexperimentation, without departing from the spirit and scope of thedisclosure. Therefore, such adaptations and modifications are intendedto be within the meaning and plurality of equivalents of the exemplaryembodiments based upon the teaching and guidance presented herein. It isto be understood that the phraseology or terminology herein is for thepurpose of description and not of limitation, such that the terminologyor phraseology of the present specification is to be interpreted bythose skilled in relevant art(s) in light of the teachings herein.

What is claimed is:
 1. A method for detecting an impairment within aservice provider network, the method comprising: developing, by one ormore computer systems within the service provider network, a firstnetwork record to record a performance of the service provider networkin delivering a service at a first instance in time; comparing, by theone or more computer systems, the first network record to a secondnetwork record that was developed to record the performance of theservice provider network in delivering the service at a second instancein time; and detecting, by the one or more computer systems, theimpairment to be present within the service provider network when one ormore characteristics, parameters, or attributes from the first networkrecord differ from one or more corresponding characteristics,parameters, or attributes from the second network record.
 2. The methodof claim 1, wherein the developing comprises developing the firstnetwork record to record a snapshot of the one or more characteristics,parameters, or attributes of the service provider network at the firstinstance in time.
 3. The method of claim 1, further comprising alertinga subscriber of the service of the impairment when present within theservice provider network.
 4. The method of claim 1, further comprisingdiagnosing, by the one or more computer systems, one or more mechanical,electrical, or electromechanical devices within the service providernetwork as causing the one or more characteristics, parameters, orattributes from the first network record to differ from the one or morecorresponding characteristics, parameters, or attributes from the secondnetwork record.
 5. The method of claim 4, further comprising repairingor replacing, by the one or more computer systems, the one or moremechanical, electrical, or electromechanical devices to remedy theimpairment.
 6. The method of claim 5, wherein the repairing or replacingcomprises dispatching a service technician to a subscriber premises ofthe service provider network having the one or more mechanical,electrical, or electromechanical devices to repair or replace the one ormore mechanical, electrical, or electromechanical devices.
 7. The methodof claim 1, further comprising receiving, by the one or more computersystems, an inquiry from a subscriber of the service whose service isaffected by the impairment that causes the service to not perform asexpected.
 8. A service provider system for detecting an impairmentwithin a service provider network, the service provider systemcomprising: a memory that stores a first network record to record aperformance of the service provider network in delivering a service at afirst instance in time; and a processor configured to executeinstructions, the instructions, when executed by the processor,configuring the processor to: develop a second network record to recordthe performance of the service provider network in delivering theservice at a second instance in time; compare the second network recordand the first network record that is stored in the memory; and detectthe impairment to be present within the service provider network whenone or more characteristics, parameters, or attributes from the secondnetwork record differ from one or more corresponding characteristics,parameters, or attributes from the first network record.
 9. The serviceprovider system of claim 8, wherein the instructions, when executed bythe processor, configure the processor to develop the second networkrecord to record a snapshot of the one or more characteristics,parameters, or attributes of the service provider network at the secondinstance in time.
 10. The service provider system of claim 8, whereinthe instructions, when executed by the processor, further configure theprocessor to alert a subscriber of the service of the impairment whenpresent within the service provider network.
 11. The service providersystem of claim 8, wherein the instructions, when executed by theprocessor, further configure the processor to diagnose one or moremechanical, electrical, or electromechanical devices within the serviceprovider network as causing the one or more characteristics, parameters,or attributes from the second network record to differ from the one ormore corresponding characteristics, parameters, or attributes from thefirst network record.
 12. The service provider system of claim 11,wherein the instructions, when executed by the processor, furtherconfigure the processor to repair or replace the one or more mechanical,electrical, or electromechanical devices to remedy the impairment. 13.The service provider system of claim 12, wherein the instructions, whenexecuted by the processor, configure the processor to dispatch a servicetechnician to a subscriber premises of the service provider networkhaving the one or more mechanical, electrical, or electromechanicaldevices to repair or replace the one or more mechanical, electrical, orelectromechanical devices.
 14. The service provider system of claim 8,wherein the instructions, when executed by the processor, furtherconfigure the processor to receive an inquiry from a subscriber of theservice whose service is affected by the impairment that causes theservice to not perform as expected.
 15. A service provider system fordetecting an impairment within a service provider network, the serviceprovider system comprising: a service provider server configured toprovide a service to a subscriber premises of the service providersystem; and an administrative workstation configured to: receive aninquiry from a subscriber of the service that is associated with thesubscriber premises and whose service is affected by the impairment;compare a first network record that was developed in response to theinquiry to record a performance of the service provider network indelivering the service at a first instance in time to a second networkrecord that was developed to record the performance of the serviceprovider network in delivering the service at a second instance in time,and detect the impairment to be present within the service providernetwork when one or more characteristics, parameters, or attributes fromthe first network record differ from one or more correspondingcharacteristics, parameters, or attributes from the second networkrecord.
 16. The service provider system of claim 15, further comprising:an administrative server configured to develop the first network recordto record a snapshot of the one or more characteristics, parameters, orattributes of the service provider network at the first instance intime.
 17. The service provider system of claim 15 wherein theadministrative workstation is further configured to alert a subscriberof the service of the impairment when present within the serviceprovider network.
 18. The service provider system of claim 15, whereinthe administrative workstation is further configured to diagnose one ormore mechanical, electrical, or electromechanical devices within theservice provider network as causing the one or more characteristics,parameters, or attributes from the first network record to differ fromthe one or more corresponding characteristics, parameters, or attributesfrom the second network record.
 19. The service provider system of claim18, wherein the administrative workstation is configured to repair orreplace the one or more mechanical, electrical, or electromechanicaldevices to remedy the impairment.
 20. The service provider system ofclaim 19, wherein the administrative workstation is configured todispatch a service technician to a subscriber premises of the serviceprovider network having the one or more mechanical, electrical, orelectromechanical devices to repair or replace the one or moremechanical, electrical, or electromechanical devices.